suggestion: maybe at this point make it chwbn, with an arg to set the border colors/widths? .

something like chwbn -n 3 -c <color> -c <color> -c <color> -w 2 -w 4 -w 2 <wids>, where each -c and -w sets the next border from inside out or vice versa.

@neeasade I'd say that suggestion may work for borders >= 4, but for just chwb3, chwb2, and chwb, I'd say it wouldn't mesh well.

Especially considering that chwb and chwb2 are in two completely different repositories, users could potentially have chwb, but not chwb2, and having chwbn would be completely useless to that demographic of users (and would take up space on their drive, moreso than is necessary).

More than 3 borders seems unnecessary, as well. Good suggestion, though, I just don't think it would apply very well in this scenario.

I would be pretty redundant to have 2 tools aside that do the exact same thing (draw a pixmap on thw borders).
As neasade said, it would be best to turn chwb2 into a more generic purpose tool, eg. dwpb for "draw pixmap on window borders" or something along those lines.

because what a user see as "unnecessary number of borders" is arbitrary (and to me, more than 1 border seem unnecessary) ;)